Miro for Microsoft Sentinel

Solution: Miro

Miro Logo

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Solutions Index


Attribute Value
Publisher Miro
Support Tier Partner
Support Link https://help.miro.com
Categories Security - Automation (SOAR),Security - Insider Threat,Security - Information Protection,Security - Threat Protection,Security - Cloud Security,Compliance,User Behavior (UEBA),Application
Version 3.1.1
Author Miro - enterprise_integrations@miro.com
First Published 2025-12-05
Last Updated 2026-10-29
Solution Folder Miro
Marketplace Azure Marketplace · Popularity: 🔵 Medium (73%)

The Miro solution for Microsoft Sentinel provides the capability to ingest audit logs, content activity logs, and AI interaction logs from Miro REST APIs into Microsoft Sentinel using the Codeless Connector Framework (CCF). This connector enables organizations to monitor and analyze activities within their Miro workspaces. For detailed instructions, refer to the documentation.

Underlying Microsoft technology used:

This solution is dependent on the following technology and this dependency may be in Preview state or might result in additional ingestion or operational costs:

• Codeless Connector Framework (CCF)

Contents

Data Connectors

This solution provides 3 data connector(s):

Tables Used

This solution uses 3 table(s):

Table Used By Connectors Used By Content
MiroAIInteractionLogs_CL Miro AI Interaction Logs (Beta) (Enterprise Plan + Enterprise Guard) -
MiroAuditLogs_CL Miro Audit Logs (Enterprise Plan) -
MiroContentLogs_CL Miro Content Logs (Enterprise Plan + Enterprise Guard) -

Additional Documentation

📄 Source: Miro/README.md

Miro

Overview

The Miro connector ingests audit logs, content activity logs and AI interaction logs from Miro REST APIs into Microsoft Sentinel using the Codeless Connector Framework (CCF). This centralizes Miro workspace activity monitoring in Microsoft Sentinel for security threat detection, incident investigation, and compliance reporting.

Data connectors

This solution includes three data connectors:

  1. Miro Audit Logs (Enterprise Plan): Organization-wide audit events including user authentication, content access, team changes, and administrative actions. API documentation | Audit logs overview.
  2. Miro Content Logs (Enterprise Plan + Enterprise Guard): Content activity tracking including item creation, updates, and deletions for compliance and eDiscovery. API documentation | Content logs overview.
  3. Miro AI Interaction Logs (Beta) (Enterprise Plan + Enterprise Guard): User interactions with AI features in Miro: the prompt received from the user, the response returned to them, and the model and tool calls made in between. API documentation | AI interaction logs overview. This connector is in Beta: the AI interaction logs API may change before general availability.

Prerequisites

General requirements

Connector-specific requirements

For audit logs connector:

For content logs connector:

For AI interaction logs connector:

Installation

There are two ways to set up the Miro connectors.

[Content truncated...]

Release Notes

Version Date Modified (DD-MM-YYYY) Change History
3.1.1 26-10-2026 Renamed the AI Interaction Logs table from MiroAILogs_CL to MiroAIInteractionLogs_CL and every AI Interaction Logs connector resource to MiroAIInteractionLogs*; queries that read the old table name must use the new one.
3.1.0 20-10-2026 Added the AI Interaction Logs CCF connector (Beta) and the ai, ai_assisted and actor columns to Content Logs; the Content Logs and AI Interaction Logs pollers now throttle paged requests. Setup steps explain that the SIEM toggle creates one token with every log scope the organization is entitled to.
3.0.0 05-12-2025 Initial release of the Miro solution with two CCF connectors (Audit Logs and Content Logs).

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Solutions Index